-
Notifications
You must be signed in to change notification settings - Fork 146
chore(gas): add overview and history docs #3879
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(gas): add overview and history docs #3879
Conversation
More templates
@rivetkit/cloudflare-workers
@rivetkit/db
@rivetkit/framework-base
@rivetkit/next-js
@rivetkit/react
rivetkit
@rivetkit/sql-loader
@rivetkit/virtual-websocket
@rivetkit/engine-runner
@rivetkit/engine-runner-protocol
commit: |
PR Review: Gasoline DocumentationThis PR adds comprehensive documentation for Gasoline's core concepts. Overall, this is a high-quality documentation contribution that will significantly help developers understand the durable execution engine. ✅ Strengths
📝 Minor Issues & SuggestionsDocumentation Content
Code Changes
TODOs
🎯 RecommendationsHigh Priority:
Medium Priority:
Low Priority:
SummaryThis is solid documentation work. The content is technically accurate, well-organized, and pedagogically effective. The main concerns are around maintaining consistency with terminology conventions (Rivet Actors) and deciding whether to include placeholder files. The typo fix in HIBERNATING_WS.md is good. Verdict: Approved with minor suggestions for consideration. The documentation significantly improves upon the original GASOLINE.md file. |
| - Separate the transactions into 2 activities | ||
|
|
||
| ## Signals | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice how it explains a bit more of how it actually works. Might be good to say blatanlty how signals are the only form of durable/guaranteed communication and they’re consumption is guaranteed ( is it?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to say "only". Signal consumption is not guaranteed, the wf needs to listen to the signals to receive them
|
|
||
| Signals can be sent to a workflow if you know its name and a subset of its tags. | ||
|
|
||
| Internally, it is more efficient to order signal tags in a manner of most unique to least unique: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this Gotchas worthy?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely
ea05c93 to
c2f846e
Compare
a35f0d9 to
e88b75c
Compare
0738934 to
8b91b37
Compare
e88b75c to
74129c7
Compare
8b91b37 to
f65fde5
Compare
74129c7 to
c3c6740
Compare
f65fde5 to
ffb8072
Compare
c3c6740 to
cdb8231
Compare
ffb8072 to
654b4e9
Compare
cdb8231 to
1353291
Compare
654b4e9 to
c023ef5
Compare
921ccb3 to
e8bbcf8
Compare
c023ef5 to
af232ee
Compare
e8bbcf8 to
d8a0135
Compare
af232ee to
1c80e13
Compare
d8a0135 to
116ea58
Compare
1c80e13 to
5889ab3
Compare
116ea58 to
708a38f
Compare
5889ab3 to
7d75756
Compare
Merge activity
|

No description provided.